use textContent instead of innerHtml, preventing XSS #3816
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
Member
|
ah, whoops. good fix, thanks |
|
Hey @Rich-Harris, any plans a pushing a new release to npm with this fix? Thanks 😊 |
Member
|
The last cut version (3.13.0-alpha.2) was before #3808, which introduced the issue. |
|
Ahhh makes sense, thanks @Conduitry |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3813
Added a new concept here,
is_static_contentbesides thecan_use_innerhtmlto differentiate cases where we can use
innerHtml:if,each, etcand cases where the content is static: